Repository navigation
Conversation
Round 50 — Fastly SDK correctness pass (commit
|
Round 51 — round-50 carry-overs + Spin WASI write mechanics (commit
|
161a244 to
93f72fe
Compare
# Conflicts: # docs/.vitepress/config.mts # docs/guide/adapters/axum.md # docs/guide/adapters/cloudflare.md # docs/guide/adapters/fastly.md # docs/guide/adapters/overview.md # docs/guide/architecture.md # docs/guide/proxying.md # docs/guide/roadmap.md # docs/guide/streaming.md
085bc23 to
4189710
Compare
|
CREATOR: Ready for re-review at The approved four-finding repair is pushed. Each original thread has a separate fixed disposition and executed evidence:
Full prescribed suite, executed locally at this exact head with non-interactive stdin, exit 0: This includes all four adapter CI suites, demo/generated workspaces and documentation/dependency contracts. Actual result lines include: Additional checks all exited 0 at this head: cargo fmt --all -- --check
cargo fmt --manifest-path crates/edgezero-test-harness/Cargo.toml --all -- --check
cargo clippy --offline --locked --workspace --all-targets --all-features -- -D warnings
cargo clippy --offline --locked --manifest-path crates/edgezero-test-harness/Cargo.toml --all-targets -- -D warnings
cargo clippy --offline --locked -p edgezero-adapter-fastly --no-default-features --features fastly,test-utils --target wasm32-wasip1 --all-targets -- -D warnings
cargo clippy --offline --locked -p edgezero-adapter-cloudflare --no-default-features --features cloudflare,test-utils --target wasm32-unknown-unknown --all-targets -- -D warnings
cargo clippy --offline --locked -p edgezero-adapter-spin --no-default-features --features spin,test-utils --target wasm32-wasip2 --all-targets -- -D warnings
cargo check --offline --locked --workspace --all-targets --features "fastly cloudflare spin"
cargo check --offline --locked -p edgezero-adapter-spin --target wasm32-wasip2 --features spin
cargo test --offline --locked -p edgezero-core --doc
npm run --prefix docs format
npm run --prefix docs lint
npm run --prefix docs buildFocused current-head verification: 33 scope tests, 50 finalizer tests, 341 Fastly WASM tests, 140 Cloudflare WASM tests and five persisted-platform tests passed. The original failing probes were retained as red/green evidence, not weakened. Core doctests additionally ran their 14 compile-fail cases successfully; ignored examples and manual hosted cases are not claimed as executed. Cargo still reports the existing Specification, plan and scoped API approval are aligned. Account mode: one-account; acting login and PR author are both Next actor: REVIEWER, to independently verify and accept/resolve the four original findings. No creator-side resolution, self-approval, merge, deployment or provider guarantee promotion. Existing manual hosted/parity qualification and other independent review requirements remain open. |
|
CREATOR: Updated re-review handoff at The four original repairs and their separate fixed replies remain unchanged. Follow-up Executed at this exact head, exit 0: All four adapter CI suites, the demo/generated projects, dependency/documentation contracts and complete native harness passed again. Expanded verification at this head also exited 0 for:
The previously failing commands were explicitly reproduced and rerun successfully: cargo clippy --offline --locked -p edgezero-adapter-fastly --features cli --all-targets -- -D warnings
cargo clippy --offline --locked -p edgezero-adapter-fastly --no-default-features --lib -- -D warningsGitHub's replacement This is an implementation handoff, not approval or hosted qualification. Account mode remains one-account ( |
ChristianPavilonis
left a comment
There was a problem hiding this comment.
📝 Review scope and assessment
Requesting changes for five grouped P2 findings: four inline lifecycle/cancellation findings and the cross-provider target-pinning finding below.
The complete source/deletion pass and dynamic reproductions were performed at pinned b65e7144cc6a0a00ecd7748cd223e280725d44d8 against e11ea3082f66ec864aabdd6007b15c4926c73b82. The PR advanced during review. I checked that these findings remain in 4f1c50a52b41ee25cc06ccdbf082849d7cc6863f and used its line numbers, but did not perform a complete review or rebuild of the seven intervening commits. Across the pinned pass, 507 current files and 29 deleted BASE files were read fully; 38 lock/generated/historical-evidence files received structural checks, not full manual semantic review or external-artifact authentication.
Blocking
- 🔧 [P2] Preserve the pinned execution target at native deployment boundaries. The following are two manifestations of the same contract/target-pairing failure, separate from the acknowledged sibling-discovery policy:
- Cloudflare:
crates/edgezero-adapter-cloudflare/src/cli.rs:1053(serve also:1198) appends passthrough arguments after the selected--configwithout rejecting source selectors. Actual Wrangler 4.83.0 dry runs through the registered adapter, using the same selected manifest, emittedselected.jsfor the control butalternate.jsafter adding that positional argument; both returned success. The selected contract can therefore be checked while a different Worker entrypoint is deployed. No deployment occurred. Validate the native passthrough before launch: reject positional entrypoints and source/config/directory selectors using value-aware parsing, retain unrelated options, and add rejection-before-launch plus ordinary-option controls. - Fastly native fallback deploy:
crates/edgezero-adapter-fastly/src/cli.rs:5434–5451, especially:5449, retains only the selected manifest's directory. A store-free, non-release application selectingfastly.review.tomlinvokesfastly compute deploy --non-interactivewithout--env review, so native Fastly reads the sibling defaultfastly.tomlinstead. Conflicting default/selected service IDs make this a potentially different deployment target even without extra arguments.--dir/-C/--envalso pass the fallback reserved-argument checks. Fake-provider probes through the actual EdgeZero CLI confirmed the missing environment selection and successful forwarding of--dir; native CLI help establishes the selector semantics. No real deployment was attempted. Preserve supported filenames through native environment selection, reject unsupported names and conflicting selectors before native launch, and regress the fallback-deploy path, not only the already-repaired serve path. Keep declared application shell commands' separate, deliberately unrestricted retargeting policy unchanged.
- Cloudflare:
The four inline blockers concern rejected-output destruction under a foreign scope, manual body results after revocation, Fastly waker retirement under a mutable borrow, and unsupervised Axum build cancellation (including assembly).
Nonblocking
-
♻️ Reclaim vacant progress slots —
crates/edgezero-adapter-fastly/src/outbound/progress.rs:419. Registration always appends, while lease drop only takes the entry. A production-module probe registered/dropped 10,000 sequential leases and retained 10,000 empty slots with zero live operations (176 bytes per slot in that fake-transport instantiation, not a measured native/hosted allocation). Shared progress also scans the historical vector. Reuse vacant entries after their unique lease is gone, or compact while preserving stable identities; no new admission cap is needed. This is demonstrated bookkeeping growth, not a hosted OOM or stronger resource-capability claim. -
♻️ Clarify canonical hook ordering —
docs/superpowers/specs/2026-10-05-pre-dispatch-request-fidelity-design.md:101–103and:224. The before-lookup description correctly fits low-levelRouterInner::dispatch; please explicitly distinguish canonical route-aware admission, which resolves/admit first and skips hooks on refusal/abort. Admitted hooks still precede route dispatch, state and middleware. The implementation andrefusal_and_abort_precede_hooks_without_reading_the_request_bodyregression follow the approved admission design; this asks for a documentation qualification, not a security fix or reordered implementation.
Praise
😃 Strong compile-time logging regression coverage — crates/edgezero-macros/tests/logging_config.rs:263 covers manifest-only rebuilds, changed emitted literals, invalid-edit rejection and runtime independence. Together with caller-hygiene cases and the shared app! emitter, this tests the actual compile-time contract rather than expansion strings alone.
Verification and limitations
Pinned-head checks passed: cargo fmt --all -- --check; strict workspace/all-target/all-feature Clippy; workspace tests (2,761 passed, two ignored); the complete isolated harness (672 passed, four ignored); feature and WASM checks; Cloudflare WASM library tests (139 passed); Spin SDK-resource tests (25 passed with the explicit Wasmtime runner); Axum CI integration; generated-workspace compilation; demo tests (60 passed); dependency/legacy/docs guards; docs lint/format/build; and the complete sentinel Node suite (135 passed). Focused adversarial probes intentionally failed their assertions and supply the inline finding evidence; passing existing suites does not cover those missing cases.
At submission, the GitHub snapshot for 4f1c50a showed 25 passing checks, three pending and one skipped, with no failed check in that snapshot. The preceding head's CLI-only Fastly Clippy item-ordering failure was addressed by the final ordering commit; pending checks are not credited as passes. No independent hosted qualification, full repaired-Fastly/Spin runtime qualification, or new-head full-suite rerun is claimed. Existing feedback addressed by the intervening commits is not reposted here. The reproduced generic Backend worker-cleanup behavior predates this PR and is intentionally excluded as a new defect.
|
CREATOR: fixed: body-only target-pinning finding in review 5928381619, in Cloudflare native deploy/serve now rejects positional entrypoints and source/config/directory/destination selectors before launch. The private value-aware grammar preserves ordinary scalar/array/optional values and aliases, handles negated booleans without swallowing a positional true/false, and rejects unknown options rather than guessing their arity. Fastly fallback deploy and serve share selected-manifest mapping: fixed nonblocking follow-ups: relinquished progress slots are reused in Full prescribed local suite and exact CI lint/docs gates passed at |
|
CREATOR: Disposition for review 5919927400, verified at
All prescribed local tests and exact CI lint/docs gates pass. Failed attempts remain disclosed; no provider guarantee is promoted. These are creator dispositions, not reviewer acceptance. |
|
CREATOR: Supplemental disposition of the earlier 17-item review, checked against
The final prescribed suite includes the isolated harness, all adapter integrations and generated/demo consumers. Exact CI lint/docs variants also pass. Earlier unconfirmed cancellation and local runtime-shutdown failures remain recorded, not claimed repaired merely because reruns pass. |
|
CREATOR: Implementation handoff at The approved scoped repairs are pushed in nine fixing/documentation commits. Each of the four new inline findings has its own original-thread reply; target pinning and both body-only reviews have linked itemized dispositions. The PR's current checkpoint now reflects this head and preserves every historical section and maintainer checkbox. Executed local evidence: complete prescribed Failed attempts remain disclosed in the repair plan and current checkpoint. The concrete fixture PID-publication race and generated-format/test-binding failures were repaired. The intermittent cancellation registration and local workerd TERM-grace failures remain unconfirmed; successful reruns do not explain or waive them. No timeout/assertion weakening, SDK-pin change, capability promotion or deployment occurred. At the latest hosted-check read: 29 successful, one Fastly WASM test job in progress. Those are separate from local evidence. @ChristianPavilonis @dhruv8sh please re-review this exact head and the explicit policy dispositions. Eight existing review threads still await reviewer acceptance/resolution, including four prior self-review fixes. CREATOR has not resolved threads or dismissed reviews. Manual hosted/parity/resource qualification remains open; this is not merge authorization. |
ChristianPavilonis
left a comment
There was a problem hiding this comment.
Summary
Approving at ea2549fb. I re-reviewed the full PR against main at e11ea308.
The five blocking items from my review at 4f1c50a5 are fixed. I read each repair commit (bd390b27, 99e17b63, 0ddf7d27, 877de7d9, 262fa4b4) and ran the focused tests: core scope/body (79), Fastly progress/scope/pinned (66) and Cloudflare pinned (2), all passing. The progress-slot reuse and the hook-ordering doc note are addressed too.
Local gates at this head all pass: cargo fmt --check, workspace clippy with -D warnings, cargo test --workspace --all-targets (2,786 passed, 2 ignored), the fastly cloudflare spin feature check, the Spin wasm32-wasip2 check and the harness suite (675 passed, 4 ignored). One environment note: 24 edgezero-cli config tests hang when stdin is a TTY, because c4_non_tty_without_yes_errors_on_consent blocks on a terminal read. That test predates this PR and passes with < /dev/null, which is how your runs invoke it.
Two non-blocking comments inline. Neither affects a production path today.
Coverage limits, so this approval isn't read as more than it is: I didn't do a deep correctness read of most of Fastly outbound.rs, Fastly delivery.rs/lifecycle.rs, Spin's WASI egress writes, Axum's egress body or the config GC writer paths, and I ran nothing hosted. For those areas I'm relying on the earlier review rounds and the passing suites.
| head_accounting: IngressHeadAccounting, | ||
| framing: IngressFraming, | ||
| ) -> Result<IngressDispatchOutcome, EdgeError> { | ||
| let head_parts = IngressHeadParts::from_request(&request, head_accounting, framing); |
There was a problem hiding this comment.
[P3] Validate the normalized head in dispatch_ingress (non-blocking)
The doc comment says adapters must call this before polling the body, but it goes straight from IngressHeadParts::from_request to begin_ingress and never calls validate_normalized. Limits set with set_ingress_head_limits aren't enforced on this path, and CL+TE or duplicate Content-Length framing gets admitted.
Nothing deployed is exposed today. All four adapters validate before begin_ingress on their own (fastly/src/request.rs:509, cloudflare/src/request.rs:642, spin/src/request.rs:396, axum/src/service.rs:259), and only tests call this function. A custom adapter that follows this doc comment would lose the checks, though, and the router only re-validates when a pre-dispatch hook is installed (router.rs:526-538).
I reproduced it from an external crate. With set_ingress_head_limits at a 16-byte target and 1 header, GET /x?<200 × a> carrying content-length: 5 and transfer-encoding: chunked went through dispatch_ingress and the handler returned 200. validate_normalized on the same head returns 414.
This mirrors what the adapters do. I applied it to a scratch copy of this head: edgezero-core clippy (all features, all targets, -D warnings) is clean and all 1,181 core tests pass.
| let head_parts = IngressHeadParts::from_request(&request, head_accounting, framing); | |
| let head_parts = IngressHeadParts::from_request(&request, head_accounting, framing); | |
| if let Err(error) = head_parts.validate_normalized(self.ingress_head_limits()) { | |
| return Ok(self.detached_ingress_error_egress( | |
| error, | |
| request.method().clone(), | |
| request_start, | |
| )); | |
| } |
A regression test sending an over-limit target and CL+TE through dispatch_ingress would pin it down. Making the function test-only would also work if it isn't meant to be a public adapter entry point.
|
|
||
| // Parse values as Wrangler does, so a value is never mistaken for a selector (or vice versa). | ||
| // Unknown options fail closed instead of guessing how many positional values they consume. | ||
| fn validate_pinned_wrangler_args(action: AdapterAction, args: &[String]) -> Result<(), String> { |
There was a problem hiding this comment.
[P3] The pinned Wrangler allowlist rejects options that select nothing, and mixes Wrangler versions (non-blocking)
The guard does what it set out to do. I checked its arities against Wrangler 4.83.0's yargs definitions with a real deploy --dry-run, and a trailing positional can't slip through. The cost is over-rejection, and the error tells the user the option would change the source, config or destination when it wouldn't:
- Wrangler 4.83.0
deploy --helphas--env-file,--triggers/--scheduleand--experimental-autoconfig/--x-autoconfig. The guard rejects all of them. - The table accepts
autoconfig, which is the 4.151 spelling, andexperimental-public-invocation, which I couldn't find in either 4.83.0 or 4.151.3deploy --help. The adapter'spackage.jsonallows^4.38.0, and the fidelity fixture pins 4.83.0. docs/guide/cli-reference.md:694-696says pinned invocations reject source/directory/environment overrides and tells users to pass other options separately or in long form. In practice any long option missing from this table is rejected too.
Impact is small. This only affects apps without [adapters.cloudflare.commands], and the scaffold declares those. I'd suggest naming the rejected token in the error and saying whether it's a target selector or just an unrecognized option, checking the table against one Wrangler version, and updating the CLI reference to say the built-in fallback forwards a fixed option set. validate_pinned_fastly_args is the same tokenizer with different tables, so one table-driven validator in edgezero-adapter/src/cli_support.rs could be a later follow-up.
PRfection phase: implementation
Current Review Checkpoint
Latest pushed head:
ea2549fb.The approved review repairs preserve the existing hard-cut outbound API, absolute deadlines/cutoffs, typed failures, resource limits, body suppression, paired clocks, completion ownership, direct native Image Optimizer path and audited pins. No compatibility wrapper, alternate transport, new public default or provider guarantee is introduced.
Prior work, including shared finalization/receipts, compile-time logging (#504) and assembly attestation, remains intact. Changelog adoption navigation now points to the current migration, dependency and capability guides; historical sections below are retained.
Local validation: the complete prescribed
bash scripts/run_tests.sh < /dev/nullexited 0, including 1,181 core tests, 675 active harness tests (four opt-in ignored), all four adapter CI integration suites, generated projects and demo/WASM checks. Exact CI formatting and Clippy combinations, including CLI-only/provider/fixture variants, and docs lint/format/build passed. GitHub checks on this new head are separate and are not claimed green.Retained failed attempts: one intermittent cancellation-helper live-group assertion remains unconfirmed; isolated and later complete harness runs passed. One local workerd shutdown exceeded the unchanged five-second TERM grace, while the fresh complete Cloudflare suite passed. Neither is claimed repaired or waived. The separate empty fixture PID-file read was reproduced and fixed by atomic publication. Template formatting/test-binding lint failures were corrected before the final complete run. Existing dependency future-incompatibility warnings remain unsuppressed.
Not merge-ready: creator dispositions are posted separately in the original inline threads and linked body-only reviews. Independent current-head acceptance, fresh GitHub checks and manual hosted/parity/resource qualification remain open. All maintainer checkboxes are unchanged. No thread resolution, dismissal, deployment, capability promotion or merge occurred.
Repair plan and evidence · Changelog · Native-target disposition · Seven-item disposition · Earlier review disposition.
Earlier Review Checkpoint (fe32185)
Latest repair:
fe32185f.The latest six review threads have separate author responses: five verified behavior fixes and one evidence-backed disagreement about removing SDK timeout readback. This checkpoint anchors Axum native timers before clock sampling, returns Spin upload failures without awaited publication, preserves mandatory framework headers through final normalization, retains Fastly terminal head errors/arrival instants, and applies one cumulative head/marker/trailer budget.
Exact committed-head validation passes: the complete prescribed suite, 2,746 workspace tests (33 binaries, zero failures, two ignored), 672 harness tests (zero failures, four opt-in ignored), all four runtime CI suites, generated-project/demo checks and all 36 additional format/lint/build/docs checks. All 30 reported GitHub checks are successful at this head. Stock Viceroy's getter abort remains a retained negative control; the explicitly selected tracked repair passes the identical SDK test without removing assertions or changing installed pins.
Not merge-ready: reviewer acceptance/disagreement resolution and the separate seven-case Fastly first-response assembly-attestation gate remain open. Hosted/manual qualification and maintainer checkboxes are unchanged. No deployment, provider promotion, review-thread resolution, dismissal or merge occurred.
Design, repair plan and executed results, changelog. Earlier sections below are historical checkpoints, not fresh validation or approval of this head.
Summary
Startup Fixture Validation Closeout (2026-11-09)
Latest pushed head:
a7d7fd0f.The test responder now owns its ephemeral listener continuously and publishes bounded PID/nonce/endpoint metadata before the first prescribed request. First-response attestation, sticky failures and the original absolute startup deadline remain intact. Production outbound behavior, hard-cut APIs, pins, limits and capability levels are unchanged.
Details: audit and plan. Manual hosted checks, independent current-head approval, freeze and durable qualification remain open. Existing manual checkboxes and review threads are unchanged. Earlier checkpoint results below are retained as history.
Signed-Origin Image Cache Policy Clarification (2026-11-09)
Pushed
c8fd1939under AG's direct approval. This carries the migration requirements from Trusted Server #1516 without changing production APIs, transport, SDK/runtime pins, deadlines, limits or capability levels.Bypasswithout optimizer options; final optimized GET usesPlatformDefaultwith options. Signing, preflight decisions and private/no-store error rendering stay application policy. No automatic extra fetch or second transport.Plan/checkpoint and verification boundaries. Hosted S3/optimizer checks, previous timing/shutdown failures, candidate freeze, durable Q5 publication and independent acceptance remain open. Fresh GitHub checks are separate. No deployment, thread resolution, dismissal or merge. Maintainer checkboxes are unchanged.
Earlier Checkpoint: Native Timer And Shutdown Investigation (2026-11-08)
Pushed
25114e66. This is a narrow Axum timer repair with co-located tests and audit/changelog updates; public APIs, SDK/runtime pins, capabilities and acceptance limits are unchanged.sleep_until; a paused-time regression fails at 120 ms before the fix and passes at the original 100 ms target afterward. Native early success remains only a wakeup, not logical expiry. Runtime/driver failures and overflow remain typed.kevent; this does not distinguish signal notification from stalled drain propagation. Four separate JavaScript-only controls pass but do not prove bootstrap causation. Temporary tracing/profiling code was removed after retaining captures; no new script, CI probe or profiler dependency ships.RUST_TEST_THREADS=2 bash scripts/run_tests.shexits 1: Axum and Fastly pass, then Cloudflare's real routing probe requires SIGKILL after the unchanged five-second TERM grace. Preserve run18e64816e16e8f68-663-0; no retry is substituted. Four focused native-timer tests also pass on the committed head.Detailed investigation and evidence limits. New-head hosted checks are separate; older green checks are not reused. No deployment, capability promotion, thread resolution, review dismissal or merge. Maintainer checkboxes are unchanged.
Earlier Checkpoint: Local Reuse And Shutdown Closeout (2026-11-08)
Pushed
ebab57ea. This is a test-harness/documentation checkpoint, not a production API or runtime-policy change.Verification is mixed. The full prescribed
RUST_TEST_THREADS=2 bash scripts/run_tests.shpasses, including all four adapter suites, generated app, demo and documentation guards. Harness: 650 passed / zero failed / three opt-in tests ignored. All 30 additional workflow format/lint/WASM/docs commands and the other four primary Rust gates pass.However, separate default-parallel and two-thread workspace runs both exit 101 on the unchanged Axum pending-upload target: 107.941125 ms and 112.950416 ms versus 105 ms. Both failures are retained, not dismissed or called pre-existing. Reduced parallelism is not an established repair; no threshold, assertion or qualification gate was relaxed.
Investigation and evidence limits. Fresh GitHub checks belong to this head and must be read separately; earlier green checks are not substituted. Reviewer acceptance, manual hosted checks, strict timing/cancellation gaps, candidate freeze and durable Q5 remain open. No merge-ready claim, deployment, capability promotion, thread resolution, review dismissal or merge.
This current status supersedes the historical checkpoints below. The maintainer's hosted checkboxes are unchanged.
Earlier Checkpoint: Fastly Callback-Ownership CI Repair (2026-11-08)
Pushed
26612053, a two-file test/changelog repair approved by AG. The original CI failure was reproduced unchanged on repetition 6; forcing a typed timer error reproduces it deterministically. The test incorrectly treated per-exchange timer destruction as callback closure, although an early connection error must release that timer immediately.The repaired test observes the managed callback scope and exactly-once callback-family resource release, covers standalone/wrapped helpers with pending/failed timers, and retains the post-callback batch
Internalassertion. Existing deterministic pending-driver cleanup tests remain unchanged. No production code, APIs, pins, deadlines, limits, assertions, capability levels or qualification gates were relaxed.RUST_TEST_THREADS=2 bash scripts/run_tests.shattempt exited 1 when the Cloudflare ingress fixture required SIGKILL after the unchanged five-second workerd shutdown grace. The unchanged retry exited 1 because Fastly smoke returned 2:custom_lazy_initialization_recoverywas unverified because all five callbacks were not observed in one guest. These failures are retained; their causes are not established and are not labelled pre-existing, waived, or converted to passing results.Fresh GitHub CI is running separately at
26612053. This is not an all-green or merge-ready claim. Existing review dispositions, manual hosted checkboxes, strict timing/cancellation gaps, candidate freeze and Q4/Q5 qualification remain open; no deployment, capability promotion, thread resolution or merge occurred.Approved Qualification Amendments (2026-11-08)
Implemented in
dcbf622funder AG's direct approval:The current handoff records current-head checks, per-thread replies and remaining review decisions. Older checkpoints below retain their historical status; they are not current completion claims.
TS Reposted Review Repairs
The six reposted TS findings are repaired in
6f0cc74c, with a separate fixed reply and executed evidence in each original thread. Reviewer acceptance remains pending; no thread was resolved by the author, and other reviewers' threads are untouched.The scoped changes complete nonblocking Fastly buffered readiness through head/data/EOF and cooperative yields, add routed AC2 expiry coverage and bindings, restore the positive Rust deferral regression, and correct the remaining checklist, idle-policy and acceptance-reference text. Public outbound contracts, hard-cut APIs, SDK/runtime pins and qualification limits are unchanged.
Validation at the exact committed head passed: all five primary Rust gates; the complete
bash scripts/run_tests.sh; and the 33-command lint/build/docs matrix covering adapter feature selections, all three WASM targets, fixtures and demo. Workspace: 2685 passed, zero failed, one existing ignored, 33 binaries. Harness: 626 passed, zero failed, two existing ignored. All four local adapter integration suites and the generated-project gate passed. The deferral spelling mutation failed as intended and was restored before the commit.The initial terminal-stdin interruption and the local Cloudflare tool-version failure are retained; the final committed-head run used noninteractive stdin and the ingress fixture's lock-matched wasm-bindgen. Fresh GitHub checks are running; they are not declared fully green. This is local validation, not a frozen or hosted qualification record.
Qualification remains open: the strict local lifetime run retained cold Begin at 8548 us against the unchanged 7000 us bound. SDK parity, unknown optimizer blocking horizon, manual hosted evidence, candidate freeze and Q4/Q5 are not waived. No deployment or capability promotion was performed. The manual hosted checklist below is unchanged.
Implements the portable outbound HTTP and request-lifecycle contracts across core and the Axum, Cloudflare, Fastly, and Spin adapters.
start_batch_until, indexednext, explicitcancel, orderedcollect, and thesend_all_untilconvenience path.start_batch_untiltakes an observation cutoff: reaching it stops observation even when individual slots retain budget, while earlier cutoffs remain a supported partial-result operation.PlatformMetadatafacts for memory ceilings, live inbound request population, and host-ingress accounting, preserving source and explicit unknown reasons.Fits,Exceeds, and typedIndeterminateoutcomes; publishes canonical Axum, Cloudflare, Fastly, generic Spin, and Akamai Functions profiles.CompletedorCutoff. OnlyCutoffpermits unresolved slots in a successful result. Explicit adapter failure, premature driver EOF, and duplicate or out-of-range indices returnOutboundBatchFailure, preserving the precise error and every terminal slot collected before failure.MonotonicClock::deadline_afteranchors relative cutoffs to that clock. Equality expiry wins and backwards time fails closed.ResponseEgressCompletion, transferred directly throughPreparedIngress,ResponseEgressEnvelope, and the soleResponseEgressAttempt. Terminal state is stored before the response-scoped completion and global observer run, each exactly once and behind independent panic boundaries. No response-extension carrier or envelope extraction bypass remains.ResponseEgressCompletion::joincomposition so independent response-owned resources share one exactly-once terminal report, and hard-cuts detached normalized errors toSend { completion, deadline } | Abortwith request-start-relative bounded deadlines.AdmissionDecision::Abort. Axum closes the owned HTTP/1 connection before body polling; Cloudflare, Fastly, and Spin return a fixed provider error at their strongest available pre-response boundary and remain conservatively classifiedBestEffort.Hooks::configureplus core-ownedApp::build::<A>(platform). Successful hooks must preserve the complete adapter-selected metadata; core rejects changed facts instead of restoring them. Typed configuration failures propagate unchanged and stop serving before request handling. The generated scaffold keeps finite ingress policy with core-owned empty lifecycle tokens; the checked-in demo retains the full application-owned resource-composition example.AbortController, Fastly's low-levelstream_to_client, and Spin's WASI response/body/result writers.Current Checkpoint: Event-Driven Workers Cancellation
Head:
9b31a697, including maincf2c57b1. Implementation and evidence boundaries.The PR is ready for review, not draft, but remains unqualified. Historical checkpoint references to draft status describe their then-current state; they are not the live PR state.
9b31a697retains 17 passed/two failed constituent scenarios, exit 1, plus failed tail validation. Cold Begin is 8 ms >7 ms; ordinary-close cancellation/cleanup is unproved. These map to 12 passed/two failed lifetime legs. All previous failures, including the preceding6e5ce765capture, remain retained; no warmup, tolerance change, reset substitution or retry-for-credit.NameInUsefail-closed rather than adopting unverified settings. Hosted controls and maintainer re-review remain open. Other non-blocking review suggestions are not silently marked resolved.Local unqualified review packet:
/private/tmp/pr275-9b31a697-closeout.tar.gz, SHA-256878876dda65f8404af5b75215631e4402c5dce80f8b73a11e0080ac5c17faa3f. It retains 52 hashed payloads plus their manifest, actual raw failures/builds, the caught fixture-ordering failure and final verification. Temporary retention is not durable Q5 publication. New-head CI runs separately; no prior-head green check is relabelled as new-head proof. Your eight manual hosted checkboxes are unchanged. No deployment, final freeze, capability promotion, review dismissal or merge is performed.Earlier Checkpoint: Workers Batch Cutoff
Head:
8f82547b. Repairs a confirmed adapter-owned scheduling gap without changing public APIs, request budgets, capability levels or SDK/runtime pins. Specification, regression and native-evidence boundaries.The local review packet contains 99 hash-verified files:
/private/tmp/pr275-cutoff-coordinator-packet.tar.gz, SHA-25627837dc0fdb5785550ced06f7666e58091508e9ac64bbd11c884d2755195be68. It preserves RED/GREEN and final verification logs, the actual native patch/build and all failures, separately from the final source patch. Temporary local storage is not durable qualification. Demo/templates require no signature migration and inherit the adapter repair. No deployment, freeze, merge or maintainer review-state change is performed; the eight manual hosted checkboxes below are unchanged. New-head CI must execute separately.Earlier Checkpoint: Exact-Head Evidence Mapping
Tracking commit:
46019b2d. This documentation-only checkpoint maps evidence for reviewed source562acc1dedbf169315853900f9395e7ff5160076; it does not freeze or qualify either revision. Audit and evidence boundaries.12287f9f; Cloudflare/Spin do not embed a source SHA. The 30 successful checks associated with reviewed head562acc1ddo not establish exact-head runtime qualification.The local review packet contains 231 hash-verified files:
/private/tmp/pr275-562acc1d-closeout-packet.tar.gz. SHA-256:d96a6a50a80b87dad910fe43e2ca71d53ea887f7711d83cc5d26867af56fc4d6. It retains the original metadata draft separately, corrected pre-freeze record, complete derived leg map, raw captures/builds and supporting CI crosswalk. This temporary archive is not durable Q5 publication. Source APIs, adapters, demo/templates, SDK/runtime pins and outbound guarantees are unchanged. No deployment, freeze, merge or change to the maintainer-managed PR review state is performed. The eight manual hosted checkboxes below are preserved unchanged.Earlier Checkpoint: Workers Timer Setup Repair
Head:
562acc1d. The reviewed repair, regressions, specification, driver plan and changelog are committed and pushed. Source is clean. Investigation and evidence boundaries.Hosted CI at this update: 30 successful / 0 neutral or skipped / 0 running or queued / 0 failed reported checks. Local verification is not a substitute for unfinished hosted checks.
A separate, hash-verified review packet contains 111 files preserving raw controls, temporary instrumentation, RED/GREEN logs, final verification and exact-commit runtime artifacts. Packet SHA-256:
00a5573ac25d504e50e1953bb585ffb043b04a7d10bb6a440268bc0e78e6eb25. Lifetime Wasm SHA-256:e4730e8f068c15ac35b7c7e28e70327fb06097d787eee7eba60fa6ac26c6c6bd. Prior macOS/Linux failures and earlier packets remain retained separately; diagnostic passes are not copied into release evidence. Local temporary storage is not durable Q5 publication.No public API, SDK/runtime pin, capability, application policy, deadline, observation cutoff or tolerance is changed. Demo/template APIs remain unchanged. No deployment, candidate freeze or merge is performed; this PR remains draft. Hosted verification remains the maintainer's checklist below.
Maintainer Hosted Verification (Manual)
The maintainer will perform and check off these hosted gates manually. No deployment is delegated. Record the exact candidate SHA and link durable evidence; unchecked means unverified, not passed. Keep documented BestEffort/Unsupported limitations unless stronger behavior is actually proved.
Local CI, parser replay and native diagnostics do not check off these hosted gates. Acceptance identities and remaining local failures stay unchanged.
Earlier Checkpoint: Completed-Test Host-Diagnostic CI Repair
Head:
f82e4025. The prior head has 29 successful checks/one failed Fastly job. Its native library reports 309 passed/zero failed, but a known host diagnostic is concatenated directly after a complete namedok; the sentinel guard incorrectly rejects that line. This checkpoint changes only that guard, its co-located tests and tracking docs.fastly-lifecycle-evidenceartifact and fail-first regressions: 103 pass/6 expected failures, covering two formats and four exact inventory environments.okimmediately followed by the existing anchored timestamped Viceroy diagnostic. Reject arbitraryok...suffixes, malformed/missing timestamps, unrelated diagnostics, failed/ignored statuses and wrong names. Preserve every sentinel, listing checks, positive zero-failure summaries, and command/stream exit handling. No workflow, invocation or inventory change.See the repair and verification tracker and original failing job.
Earlier Checkpoint: Absolute Deferred Batch Dispatch
Head:
158b0c0e. This checkpoint corrects the existing lifecycle fixture, not production outbound behavior. APIs/adapters, SDK/runtime pins, original deadlines, caps, acceptance identities and capability levels remain unchanged.DeadlineExceeded1,001 ms, original per-call deadlines 1,034 ms. The complete local suite still exits 1, with 16 pass/3 fail plus a final-log-tail failure: cold Begin entry 9 ms, pending-body cutoff 206 ms, and ordinary-close cancellation remain unqualified. Pending-head cutoff returns at 204 ms in this run; earlier failed observations are not erased. Retain the initial missing-workerd preflight as unverified exit 2.See the current tracker and audit.
Earlier Checkpoint: Native Spin Result Before EOF
Head:
8fbc4f83. This checkpoint changes the existing Spin SDK controls, validation and retained evidence only. Production APIs/adapters, SDK/runtime pins, original deadlines, acceptance identities and capability levels are unchanged.See the native record, pinned source analysis and implementation tracker.
Earlier Checkpoint: Explicit Reset Diagnostic
Head:
cd214362. This checkpoint changes test tooling and evidence only. Production outbound APIs, adapters, SDK/runtime pins, original deadlines, caps, acceptance identities and capability levels are unchanged.RequestCancelled, exactly-once SDK/source release, healthy survivor work and a clean diagnostic tail. Ordinary close still fails, with no victim terminal through the original coordination window. Reset success is diagnostic only, not a replacement acceptance gate.See the current diagnostic and runtime tracker.
Earlier Checkpoint: Native Runtime Boundaries And Linux Connect
Head:
f036425b. Production adapters, public APIs, provider pins, deadlines, caps and original acceptance identities are unchanged.defaultsocket in the existing Workers fixture launcher using the pinned Miniflare API. No entry-forwarding fallback; the SDK entry/control listener remains on a distinct ephemeral loopback port. Guest flags, modules, bindings, persistence and owned shutdown remain intact. Standard serve/deploy paths are unchanged.qualified:false; external, conditional and unpromoted scope is unchanged.See the current tracker and canonical Linux connect evidence.
Earlier Checkpoint: CI And Local Lifecycle Repairs
Head:
22c6386c. All 217 required-local acceptance legs now have executable bindings (255 criteria/511 legs; 246 ready/265 planned overall). Binding completeness is not passing runtime qualification. External, conditional and unpromoted scope remains unchanged.See the current implementation and evidence tracker for exact observations and remaining gates.
Earlier Checkpoint: Fastly Post-Delivery Batch
Head:
775366fd. Extend the existing D6 lifetime suite with a three-slot batch created after canonical response handoff, using the same retained client and original request clock. Preserve 34 ms batch entry, 534 ms cutoff and one-second per-call timeouts. No production API, SDK/runtime pin, capability or CI invocation changes.Earlier Checkpoint: Fastly Trickling Slots And Live-Batch Send
Checkpoint
f0ce2b38adds EZ-6 criteria 7/8 to the existing Fastly fixture and lifetime suite. Production outbound APIs, transport, scheduler, deadlines, limits, SDK/runtime pins and CI invocations are unchanged.See the master/D6 tracker, SUITES.md and changelog for exact scope and retained results.
Earlier Checkpoint: Fastly Origin-Body Arrival Coverage
Checkpoint
eb8ac5dfadds the missing EZ-6 criterion 6 case to the existing Fastly lifetime suite. No new runner, transport, scheduler, SDK probe, production API/policy, pin or CI invocation.See the current master/D6 tracker, SUITES.md and changelog for exact scope and evidence.
Earlier Checkpoint: Fastly Native Body-Readiness Witness
Checkpoint
5950548dadds the distinctly labelled, request-owned test-only Fastly native readiness witness. Production outbound APIs, deadlines, B31 policy, limits, SDK/runtime pins and CI invocations remain unchanged.See the implementation tracker, SUITES.md and changelog for scope and retained evidence. Demo/templates require no migration for test-only metadata.
Earlier Checkpoint: Spin Native Pending-Body Witness
Checkpoint
92e03fe8extends the existing request-owned, test-only native witness to Spin. Production outbound APIs, transport, deadlines and resource policies are unchanged.See the implementation tracker, SUITES.md and changelog for the verified scope and retained evidence. Demo/templates need no change for this test-only integration.
Earlier Checkpoint: Cloudflare Native Module Manifests
Checkpoint
deb00840repairs the existing local launcher for the selected Wrangler 4.131.0 / Miniflare 5.20260910.0-alpha / workerd 2026-09-10 combination. Production outbound APIs and adapters are unchanged.persist/v3layout, startup attestation, private diagnostics and owned disposal. Both smoke modes pass, including seeded config, declared-KV and outbound-progress checks. A separate bounded local diagnostic proves namespace...02survives process restart and is read before another write.See the current implementation tracker and SUITES.md for exact scope, checks and retained evidence.
Earlier Checkpoint: Native Pending-Body Witnesses
Checkpoint
3523e121adds finite, request-owned test-only SDK observations on Axum and Cloudflare. Prepared URI, clock, mode and budget come from shared dispatch; production policies are unchanged.CI follow-up
c6f3aaf0uses canonicalobservation_cutoffnaming. The unchanged guard, 28 Axum contracts and strict lint pass locally; all 30 reported checks passed at that checkpoint.next, beforecollect. Require full controller-selected target/origin identity, Batch/BatchCutoff, the original deadline, Pending before cutoff and release between cutoff and return. Preserve 34/200/205 ms targets and zero-head/read control.rootPathagainst the owned config directory with sanitized errors.modulesRules. Failed runs get no credit; SDK-reader unit tests do not substitute for actual fetch/runtime proof.See the implementation tracker and SUITES.md for exact checks and retained failures. The prior Fastly dispatch checkpoint retains its SDK-dispatch-only scope and three guarded proofs.
The previous focus compiler checkpoint added numeric and compiler ownership through the existing grouped Rust check; its 434-test harness and other verification remain recorded separately, not relabelled as fresh evidence. Earlier provider-boundary proofs, typed-focus approval/CLI lint, audit formatting and tooling consolidation retain their scopes and open gates.
Earlier Checkpoint: Registration Observations And Connect Capabilities
outbound-connect-timeout: Fastly declares independent provider-backed support as Native; Axum, Cloudflare and Spin retain BestEffort acceptance. Fastly's split-free flexible phase budgeting is Native. These declarations do not qualify hosted connect precision, DNS/TLS coverage, blocking-call preemption, deadlines or cancellation.Checkpoint:
2cbbc549, following registration observations at00a9edbd. The implementation tracker records exact scope, evidence and remaining gates. This checkpoint is historical; current readiness and check status are recorded above.Earlier Checkpoint: Response-Owned Outbound Handoff
Checkpoint:
abbc2c11. Detailed local artifacts and failures are recorded in the D6 response-handoff tracker checkpoint.Earlier Checkpoint: Core Mixed-Observation Acceptance Binding
EZ-6/acceptance/22@unit/core, replacing its placeholder with five executable receipt/accumulator proofs. Run six exact three-slot cases: fresh and mixed check/next/collect under Completed, Cutoff and an original typed driver failure. Stage terminal production after both mixed receipts transfer.--lib outbound::; discover all 56 exact sentinels, including the original 51 redirect proofs. No new job or per-test CI list. The old redirect-only selection fails before execution because it omits the five batch proofs. Use the shared raw Cargo log path without relabelling older evidence.Checkpoint:
279c5a93.Earlier Checkpoint: Buffered Cap During Batch Progress
caps-while-waitinglifetime case through the production clients: 128 KiB decoded gzip trickling over 300 ms, independent 1 MiB decoded / 64 KiB buffered / 256 KiB encoded limits, healthy B/C siblings, and the original 34/534 ms batch timeline.Checkpoint:
8c11307d. Final local artifacts and individual failed timing preconditions are recorded in the D6 buffered-cap tracker checkpoint.Earlier Checkpoint: Reviewed Spin SDK Integration
6c59ed5b4fcb377072763aee0b27a3abdd8edb72(WASIp3 0.10.0 / wit-bindgen 0.63.0). Align the root, demo, reusable/request-fidelity fixtures, generator and all four application lockfiles.Checkpoint:
87b5e1ce. These are local regression results, not a frozen candidate or hosted qualification. D6 closure, native body-entry evidence, consumer acceptance and hosted qualification remain open. The acceptance inventory remains 32 ready / 479 planned and unqualified.Earlier Checkpoint: Fourth-Slot Per-Call Expiry
Implemented in cd8e77e4, within the approved D6 acceptance work:
Earlier Checkpoint: Readiness-Driven Test Origins
Implemented in d3f48564, under the requester's scoped fixture-accept approval:
CI diagnostic follow-up 11b8f2c4 adds underlying errors to two existing request-fidelity version-test assertions. The prior Linux workspace failure occurred before the collector tests; its OS/process cause was not exposed and remains unproven. The fresh run passes both the request-fidelity step and the complete shared-harness tests on Linux. No test conditions, retries, version policy or subprocess behavior changed; other CI checks and provider qualification remain separate.
Earlier Checkpoint: Same-Client CPU Calibration
Implemented in 0d09236a, under the requester's scoped calibration approval:
Earlier Checkpoint: CPU Stretch Characterization
Implemented in 44baaf3b:
Earlier Checkpoint: Pending Cutoff Lifetime Probes
Implemented in 73ed39ba, following the main integration:
host-head-written-only, not proof that the SDK consumed headers or entered a body read. Full criterion 16, remaining D6 work and hosted qualification stay open. Production outbound code, signed SDK/decoder pins, frozen requirements/interfaces and capability levels are unchanged; inventory remains 32 ready/479 planned and unqualified.Earlier Checkpoint: Coordinated Spin SDK Executor Upgrade
Implemented in 7b68f737:
e65ff90dadf4173b08b14194e878ad3acd555337; its DCO check passes. Upstream Rust 1.94 CI remains separate from local Rust 1.98.1 verification.spawn_local. Root, demo, reusable fixture and generator use identical Git URL/revision and package version; guards compare all three. Lock changes stay within the affected SDK/bindings/macro graph. Decoder/map contracts remain unchanged.qualified: false; full acceptance binding, candidate freeze and authorized hosted qualification remain open.Earlier Checkpoint: Begin/Batch Lifetime Probes and SDK Gap
Implemented in 834a009e:
wit-bindgen 0.57.1.qualified: false. CPU-stretch, remaining lifetime/registration/consumer acceptance, candidate freeze and authorized hosted qualification remain open.This is a verified test/diagnostic checkpoint, not a passing full lifetime suite or completed feature qualification.
Earlier Checkpoint: Standalone Test Harness and Redirect Bindings
Implemented in b5f94c70:
crates/edgezero-test-harness, with a non-published standalone workspace and its own lockfile. Remove the old runner package/directory without an alias or duplicate implementation. Keep deployable fixture apps separate and unit/contract tests in their owning crates.qualified: false. Readiness records executable assertions, not consumer adoption, applicability approval or exact-candidate qualification.This completes the approved runner relocation and local redirect binding checkpoint, not the whole adoption plan. Lifetime/registration acceptance, successful native optimizer transformation/redirect/performance evidence, consumer integration, candidate freeze and authorized hosted qualification remain open. Optional idle-body policy is not silently adopted. No deployment, capability promotion or production outbound behavior change occurs.
Earlier Checkpoint: Local Workerd Redirect Acceptance
Implemented in 4e64db99:
outbound-wirematrix and bounded two-origin servers as Spin. A fixture-only route obtains the production client from the canonical request context; no Fetch replacement, parallel outbound transport or new host-language runner is used.Successful native optimizer redirects, conditional idle-policy coverage, complete criterion-level binding and consumer/hosted acceptance remain open. The inventory remains eleven ready legs, 500 planned and
qualified: false.Earlier Checkpoint: Rust Spin Wire Harness
Implemented in 361da4f1:
--adapter spin --suite outbound-wirein the existing Rust fixture harness. No Python or Node replacement runner, compatibility wrapper, dependency changes or second process supervisor remains.This checkpoint is test-tooling only. No hosted deployment, capability promotion, candidate freeze or optimizer performance claim is made. The inventory remains eleven ready legs, 500 planned and
qualified: false.Earlier Checkpoint: Provider Redirect Boundaries
Implemented in 699cd49c:
Workerd/origin parity, successful optimized-first-hop redirects, conditional idle-policy coverage, complete criterion-level acceptance binding, candidate freeze and consumer/hosted qualification remain open. Native optimizer dispatch is preserved; unavailable-boundary controls do not establish transformation or performance. No deployment is performed. The inventory remains eleven ready legs, 500 planned and
qualified: false.Earlier Checkpoint: Fastly Cooperative-Wake CI Repair
Implemented in f57b8130:
qualification: false.Still open: provider-runtime redirect acceptance, exact-candidate criterion bindings, resource-policy decisions and consumer/hosted qualification. All previous outbound guarantees and direct native Image Optimizer integration remain intact.
Earlier Checkpoint: Explicit Redirect Following
Implemented in e02c2360:
HttpClient::followAPI with a required synchronous application policy and validated 1..=20 redirect limit. Plain Send, Begin and Batch remain unfollowed.Still open: other provider-runtime Follow parity, actual Fastly optimizer-hop mapping, consumer composition, exact-candidate criterion bindings, resource-policy decisions and hosted qualification. The inventory remains eleven ready legs, 500 planned and
qualified: false. No deployment or capability promotion occurred, and the PR remains draft. Current tracker.Earlier Checkpoint: Shared Outbound Pipeline and Ownership
Implemented in 2be1dd87:
Open at that checkpoint: explicit same-client redirect following (now implemented in the checkpoint above), remaining exact-candidate acceptance bindings, resource-policy decisions and hosted qualification. Local runtime evidence does not promote capabilities or prove end-client delivery. The PR remains draft. See the current tracker.
Earlier Checkpoint: Live Paired Time
Implemented in d86d4c0d, with the isolated Cloudflare test-ordering correction in f4d660b1:
with_time/ Axumtry_with_time, removing clock-only constructors without aliases.OutboundTimefor live asynchronous deadline handling. Check timers before source polling, preserve operational errors and diagnostics, retain clock high-water observations across chunks/yields, and release terminal/cancelled ownership.This completes only the approved sequencing checkpoint. The public head-first trait, settlement/context issuance, batch receipts, eager Begin, redirect integration and hosted qualification remain open. Requirements and frozen Plan 02 hashes are unchanged. See the verification audit.
Earlier Checkpoint: Bounded Synthesized Headers
Added in
d47c8026:This checkpoint is not completion of the broader adoption plan or hosted qualification. The full head-first/eager/redirect migration, Fastly's failed G2 preserving-read proof, all nine failed Fastly framing SDK parity controls, Cloudflare overflow recovery, consumer integration and exact-candidate hosted qualification remain open. No capability is promoted, no compatibility layer is restored, and the PR remains draft.
Reviewer correctness follow-up
Addressed R1–R4 in
92111839:Main merge and shared-policy follow-up
Addressed R5 and R6 in
91f4af38, merging main683202c6without restoring superseded APIs:OutboundBatch::from_futures; adapters retain preflight validation, exchange ownership, clocks, and terminal samples. Ready results remain retained, driver EOF/index invariants remain enforced, and cutoff releases pending futures before reporting termination. Fastly retains its distinct provider-handle driver.ResponseBodyPolicyandapply_response_body_policy, preserving declared-length checks, encoded limits, decoding/header rewriting, decoded limits, passthrough, and rechunk order. Transport reads, bodyless handling, deadlines, cancellation, and final buffering remain adapter-owned.Result<(), E>through a wrapper that prevents SDK-generated second responses.R7's dependency-audit-script deduplication remains deferred; dependency contract checks remain unchanged and pass.
Bounded native ingress and config follow-up
ConfigValuereturns. Axum constructors requireConfigStoreLimits;from_mapis fallible. Reads share payloads, and local config push updates require a server restart.serde_json 1.0.150, hash canonical JSON incrementally, and release extraction's raw handle before secret retrieval. A moving-reallocation malformed-root probe measured 36,428 requested peak bytes under a 100,060-byte staging cap, with zero retained bytes after rejection.Unsupportedand response egress remainsBestEffort. Local emulators and guest contract tests are not deployed runtime evidence.Bounded provider reads and lifecycle qualification infrastructure
FinalizationRegistrycleanup support. Generated and demo Workers explicitly enableenable_weak_ref, and regression tests inspect their TOML rather than assuming an exact one-flag string.try_opennow returns typedConfigStoreError.Downstream acceptance impact
Cloudflare
outbound-deadlinesandstreamed-upload-deadlinesareBestEffort, notNative. Downstream acceptance suites must use best-effort deadline wording and must not claim exact cancellation enforcement until deployed host-observed evidence exists.The response completion, ingress abort, and fallible application-assembly changes are intentional breaking changes. Consumers must provide a completion on every response-producing admission decision and propagate
App::build::<A>(platform)failures.Evidence boundaries
Capability declarations remain conservative where provider behavior is not proved:
Unsupportedon all adapters.Nativeon Axum andBestEfforton Cloudflare, Fastly, and Spin because finite host-side teardown is not proved or synchronously preemptible.Nativeon Axum's owned HTTP/1 connection andBestEfforton Cloudflare, Fastly, and Spin because provider transport reset/close is not directly observable.BestEfforton every adapter because no boundary proves end-client receipt; provider-specific blocking and teardown limits are documented.Unsupported; provider parsing/materialization, SDK copies, informational responses, trailers, allocator overhead, and other host-owned memory remain outside guest-visible caps.BestEfforton every adapter because provider operations are not proved cancellable within a finite wall-clock interval.BestEffortpending a deployed host-observed cancellation artifact. Fastly and Spin retain their separately documented deadline and isolation limitations. Fastly declares split-free phase budgeting Native; its independent connect setting remains unqualified for hosted timing precision.Validation
This checklist records validation across PR checkpoints. The exact latest reruns and remaining acceptance failures are listed above; it is not a claim of hosted qualification or a fresh run of every historical matrix.
scripts/run_tests.shcargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-targetscargo check --workspace --all-targets --features "fastly cloudflare spin"Closes
Closes #504.
Closes #505.
Closes #506.
Closes #109.
Closes #113.
Closes #147.
Closes #148.
Closes #436.
TS cutover follow-up, November 11
Adds an optional read-only received-head preparation callback for structurally validated input. Applications retain authenticated facts before native sanitation; this cannot read a body, change headers, bypass admission, or return a response. Existing admitted pre-dispatch hooks retain their timing.
Current head:
410a16238b7cb740275ad69b9af628cd52c57bdc.Local combined-RC qualification at
36f8e9c9c2c93661aaa73f2ca956cec3bc9e4c92: workspace tests 2,947 passed / 6 ignored; all-feature Axum 568 passed, including 36 production-hosting, 6 AWS startup and 4 celld startup cases; core doctests 19 passed / 13 ignored; strict workspace Clippy, formatting, feature compilation and Spin WASM check passed under Rust 1.98.1. Narrow TS consumer proof under Node 24.20.0: all four real proxy tests and typed prepared config/secrets/router startup passed. This is not final TS-stack/image/deployment qualification. Fresh hosted checks are still required.Retained callback-scope fixture follow-up
Commit
14a6ca8bb5a5cbe055a1f725bdab8f42569a3bf0removes an IO-timing assumption fromretained_client_resolves_fresh_callback_scope. The original test failed locally on repetition 3 because both observed batch slots could already be complete after a legitimate loopback refusal. The fresh-callback observation is retained, then a new unpolled batch is retained for the unchanged stale-scope Internal assertions. Callback count remains exactly two. Production code, deadlines and completion semantics are unchanged. All 20 fixed filtered repetitions, the complete 325 Fastly WASM unit tests and strict Fastly WASM Clippy pass with the explicitly repaired local Viceroy. Fresh hosted verification is running.